Websydian v6.1 online documentationOnline documentation - Websydian v6.5

Error running new WebsydianExpress Windows installation

Relevant for

WebsydianExpress for Windows, WebsydianExpress for Windows - iSeries

Installations on Windows 7 / Windows Server 2008

Symptoms

You have installed WebsydianExpress, the jobs has been started - but when you access the application you get an error.

The webservercomponent.log file states that there were no available tokens for the specified service.

The ApplicationServices.Log file contains errors indicating that the application service can't connect to the Websydian Server.

Cause

The problem occurs because WinC in Windows 7 and Windows Server 2008 both has IP version 6 as default - while Java (which the Websydian Server is built in) has IP version 4 as default.

This effect of this is that the application services can't connect to the Websydian Server - and the application does not work.

Solution

To make the WinC objects and the Java objects default to the same IP version, you need to change or create a registry setting:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TCPIP6\Parameters

Value name

Value data type

Value data

Description

DisabledComponents

DWORD

Hexadecimal 20

To use IPv4 instead of IPv6 in prefix policies

Use the regedit command to open the registry maintenance, navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TCPIP6\Parameters.

In many cases, the setting will no defined, create a new setting - remember to specify DWORD for the type.

Specify 20 (as a hexidecimal value) for the setting.

This setting will not disable IP version 6, it will just make IP version 4 the default version.

You must restart the system after creating/changing the setting.

You can read more about the DisabledComponents setting here:

Also note that we have located some performance issues caused by Windows 2008/7 architecture. To learn more, read the document: